Bump OpenSource-For-Freedom/Legion_runner from 1.0.42 to 1.0.51 in the actions group - #30

Sourced from OpenSource-For-Freedom/Legion_runner's releases.

v1.0.51

Added

• Curated egress presets (allowed-presets): opt-in per-ecosystem allowlists (npm, yarn, pnpm, pip, pypi, cargo, rust, go, maven, gradle, nuget, apt, debian, docker) so block mode "just works" for common toolchains without hand-listing endpoints. e.g. allowed-presets: "cargo, apt". Unit-tested.
• Download integrity verification: the action verifies the legionr-bpf / legionr-fim release binaries against a .sha256 sidecar before running them (the release now attaches the checksums), and fails closed — an unverified/corrupted/tampered download is rejected and the action degrades instead of executing it.
• learned-baseline input (default true): in block mode, also allow destinations previously learned into the Actions cache. Set false to enforce ONLY the explicit allowlist (inline + policy-file + GitHub) with no cache read/write — used by the enforce self-test for deterministic deny.
• File-integrity / tamper detection (Rust legionr-fim agent): snapshots high-value tamper targets at job start (credential/config files, .git config + hooks, and checked-out source) and diffs them at job end, surfacing anything overwritten, deleted, or chmod'd in the summary. Only sha256 hashes are stored — never contents. New inputs file-integrity (auto|off) and fim-extra-paths. file-integrity: auto downloads the agent from the latest release (plain stable Rust, no eBPF toolchain) and degrades to a silent skip if unavailable. Logic lives in legionr-core::fim (unit-tested); the binary is a release asset like legionr-bpf, built + attached by release.yml.
• Package repositories roll-up (📦): the summary now classifies named outbound destinations into their ecosystem/registry (npm, PyPI, crates.io, apt, Docker, Go, NuGet, Maven, Gradle, RubyGems, Alpine, GitHub) and shows a Package repositories reached table — registry, ecosystem, connections, and the process that reached each. Supply-chain risk hides in which registries a build talks to, so we surface them directly instead of leaving you to read IPs. Bare IPs that never got a forward name get a coarse CDN/provider hint (Fastly/Cloudflare/GitHub) via CIDR match — honest about ambiguity (a shared CDN can't name a registry). Logic in action/repos.js, fully unit-tested.
• Combined cross-job egress report (one summary for the whole run): GitHub has no run-level summary, so each job emits its captured egress as a JSON artifact (node action/report.js emit) and a final egress-report job merges them into a SINGLE table — which job + process reached what — with a package repositories roll-up and a per-job diagnostics block (render). Wired into CI; render is pure and unit-tested. Pairs with job-summary: false so the run shows one combined summary instead of one table per job.
• job-summary input (default true): set false to keep monitoring and enforcement fully active but suppress the connections table in the job summary. Useful when many jobs in one workflow each run the action and you only want the table once (our own CI uses it so a run shows one table, not one per job).
• Secure diagnostics line in the summary: reports which resolution path actually fired (forwarder on/off · captured DNS records N · getaddrinfo route … · named X/Y destinations) so a run that comes back as bare IPs is triagable. Secure by construction — only booleans, counts, and a fixed enum; never the upstream resolver IP, file paths, captured hostnames, or env values.

... (truncated)

• c87551e feat(harden): refresh the egress allowlist on a timer (#72) (#81)
• b719e39 test(e2e): drive install -> provision -> harden -> serve one job (#75) (#80)
• fdd9bef build(deps): bump the actions-minor group with 2 updates (#79)
• 016f7f3 feat(runner): Tailscale integration for ephemeral runners (#77)
• 17dc4d8 fix(runner): resolve egress IPs, back off crash loops, give jobs a writable H...
• f043a98 security(runner): strip LEGIONR_TOKEN/GITHUB_TOKEN from the job environment (...
• 81f1fa7 fix: shorten action.yml description under the 125-char Marketplace limit (#69)
• 7c25b38 build(deps): bump the actions-major group across 1 directory with 3 updates (...
• fff6441 ci: bump the dogfood action pin to v1.0.43 (#68)
• 98a89ac deps: bump quinn-proto to 0.11.15 (RUSTSEC-2026-0185) (#67)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions